Upgrade to PowerShell 7#16075
Open
JunielKatarn wants to merge 47 commits intomicrosoft:mainfrom
Open
Conversation
…mands to Windows PowerShell
Performance Test ResultsBranch: ✅ Passed161 scenario(s) across 28 suite(s) — no regressionsSectionList
FlatList
TouchableOpacity
ScrollView
TouchableHighlight
Pressable
Modal
Image
ActivityIndicator
Switch
Button
TextInput
View
Text
SectionList.native-perf-test.ts
FlatList.native-perf-test.ts
TouchableHighlight.native-perf-test.ts
TouchableOpacity.native-perf-test.ts
Pressable.native-perf-test.ts
ScrollView.native-perf-test.ts
ActivityIndicator.native-perf-test.ts
TextInput.native-perf-test.ts
Switch.native-perf-test.ts
Button.native-perf-test.ts
Modal.native-perf-test.ts
Image.native-perf-test.ts
View.native-perf-test.ts
Text.native-perf-test.ts
|
dannyvv
approved these changes
May 4, 2026
| } | ||
| } catch {} | ||
|
|
||
| return `${process.env.SystemRoot}\\System32\\WindowsPowerShell\\v1.0\\powershell.exe`; |
Member
There was a problem hiding this comment.
You are changing the compatiblity matrix here. The old powershell was assumed to be part of windows and is fully backwrads compatible... Now you make the repo control the version via a specific version in nuget....
Since the feature set is massively different I can see us starting depend on 7.x features...
So then if it can't find it we'll get weird errors that can be confusing...
Especailly since above we search for it globally installed...
My preference is if NOT in global packages error out HARD and tell folks to run nuget to get the package...
That way we are guaranteed to have all engineers have the same version...
If you do a path fallback. Please add a check for the version to make sure the user (or CI) has globally installed the same version... And provide instructions how to upgrade if not there....
Just never fall back to v4...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Why
PowerShell 7 offers multiple performance improvements over Windows PowerShell (5.1).
🔍 PowerShell 7.x vs Windows PowerShell 5.1 — Performance & Security
ForEach-Object -Parallel) 【3-bc07e3】See https://techieramesh.com/devops/windows-automation/ps-5-1-vs-7-5-comparison/
What
vnext/dotnet-tools.json). (NuGet package to reduce set up footprint on the developer's machine).powershell.exewithpwsh.exe(except CMD and MSBuild files, for now).@react-native-windows/find-dotnet-toolsto provide a common set of functions to determine PowerShell's (and potentially any other DotNet tool) location.Testing
CI checks pass
Microsoft Reviewers: Open in CodeFlow